From a0f7344742ceabe69411f5c12d1e6a50b2891566 Mon Sep 17 00:00:00 2001 From: Pietro Albini Date: Sun, 4 Sep 2016 21:56:05 +0200 Subject: [PATCH] Remove reference of Rust 1.11.0 release date in the FAQ This commit also reflows the text after removing the reference. --- src/doc/faq.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/src/doc/faq.md b/src/doc/faq.md index 96272fefd..cf92bbe2c 100644 --- a/src/doc/faq.md +++ b/src/doc/faq.md @@ -178,14 +178,14 @@ and a populated cache of the crates reflected in the lock file. If either of these components are missing, then they're required for the build to succeed and must be fetched remotely. -As of Rust 1.11.0 (to be released 2016-09-29) Cargo understands a new flag, -`--frozen`, which is an assertion that it shouldn't touch the network. When -passed, Cargo will immediately return an error if it would otherwise attempt a -network request. The error should include contextual information about why the -network request is being made in the first place to help debug as well. Note -that this flag *does not change the behavior of Cargo*, it simply asserts that -Cargo shouldn't touch the network as a previous command has been run to ensure -that network activity shouldn't be necessary. +As of Rust 1.11.0 Cargo understands a new flag, `--frozen`, which is an +assertion that it shouldn't touch the network. When passed, Cargo will +immediately return an error if it would otherwise attempt a network request. +The error should include contextual information about why the network request is +being made in the first place to help debug as well. Note that this flag *does +not change the behavior of Cargo*, it simply asserts that Cargo shouldn't touch +the network as a previous command has been run to ensure that network activity +shouldn't be necessary. For more information about vendoring, see documentation on [source replacement][replace]. -- 2.30.2